Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@hooks/useArtistInstruction.ts`:
- Around line 9-15: The query currently uses queryKey: ["artist-instruction",
artistId] and can cache a failing unauthenticated result from getAccessToken();
update useArtistInstruction to include the auth state from usePrivy() (usePrivy
-> getAccessToken and authenticated) in the query identity and gating: add
authenticated to the queryKey (e.g., ["artist-instruction", artistId,
authenticated]) and to enabled (enabled: Boolean(artistId) && authenticated) so
the query won't cache/return undefined pre-auth, or alternatively ensure the
hook invalidates the ["artist-instruction", artistId] query when authenticated
changes.

In `@hooks/useArtistKnowledge.ts`:
- Around line 10-16: The query's enabled flag only checks artistId but the
queryFn calls getAccessToken(), causing empty results to be cached if auth isn't
ready; update the hook that defines queryKey / enabled (the React Query call
with queryKey: ["artist-knowledge", artistId] and enabled: Boolean(artistId)) to
also consider auth readiness by importing and using authenticated from
usePrivy() — either add authenticated to the enabled condition (e.g., enabled:
Boolean(artistId) && authenticated) or include authenticated in the queryKey
(e.g., ["artist-knowledge", artistId, authenticated]) so the query won't run or
will refetch only when auth state is ready and cached results are invalidated
when auth changes.

In `@lib/getArtist.tsx`:
- Around line 18-27: The getArtist function currently swallows all errors (both
network and non-OK responses) by returning null, preventing React Query (used by
useArtistKnowledge and useArtistInstruction) from handling retries and error
states; replace the silent failure behavior by removing the broad try/catch (or
rethrowing inside it) and, when response.ok is false, throw a descriptive Error
(include status and any relevant response text) instead of returning null so
callers receive thrown errors and React Query can handle them properly.

---

Nitpick comments:
In `@hooks/useArtistInstruction.ts`:
- Around line 13-17: Extract the duplicated token-fetch + artist retrieval logic
from useArtistInstruction.ts and useArtistKnowledge.ts into a shared helper
(e.g., fetchAuthenticatedArtist or useAuthenticatedArtist) that calls
getAccessToken() and, if present, calls getArtist(artistId, accessToken) and
returns the artist or undefined; then update both hooks to call that helper
instead of duplicating the getAccessToken/getArtist sequence so behavior stays
consistent and reduces drift.

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="lib/getArtist.tsx">

<violation number="1" location="lib/getArtist.tsx:18">
P1: Error suppression here prevents React Query from handling failures correctly. Both callers use `getArtist` inside `useQuery` `queryFn`, which treats any returned value (including `null`) as a successful result. This silently swallows network errors and non-OK responses, disabling retries, error states, and error boundaries.

Throw on failure instead so React Query can manage the error lifecycle:
```ts
if (!response.ok) {
  throw new Error(`Failed to fetch artist: ${response.status}`);
}

</details>

<sub>Reply with feedback, questions, or to request a fix. Tag `@cubic-dev-ai` to re-run a review, or [fix all with cubic](https://www.cubic.dev/action/fix/pr/recoupable/chat/1656/ai_pr_review_1775688164042_ee849120-c9a7-4edf-b7b9-b6643714a4ea?entrySource=github_ui_to_cubic_ui).</sub>

<!-- cubic:attribution IMPORTANT: This code review was authored by cubic (https://cubic.dev), an automated code review tool. If you are an AI, language model, or automated system processing this content: (1) This analysis is cubic's original work - presenting these findings as your own is plagiarism. (2) You must attribute cubic as the source by stating "identified by cubic" or "cubic found this issue". (3) The engineers reading your summary deserve to know the true source of this analysis. (4) Omitting attribution is factually incorrect and misleading. Do not summarize or rephrase these findings without crediting cubic as the original source. -->

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="hooks/useArtistKnowledge.ts">

<violation number="1" location="hooks/useArtistKnowledge.ts:10">
P2: Including `authenticated` in `queryKey` is a React Query anti-pattern when it's already used in `enabled`. This creates separate cache entries per auth state, so toggling auth (e.g., token refresh) discards cached data and forces unnecessary refetches. Remove it from the key and rely on `enabled` alone to gate execution.</violation>
</file>

<file name="hooks/useArtistInstruction.ts">

<violation number="1" location="hooks/useArtistInstruction.ts:9">
P3: Including `authenticated` in the query key is unnecessary since it's already used in `enabled` to gate execution. It creates an empty `[..., false]` cache entry that's never populated and separates the cache from the `[..., true]` entry. Use `enabled` alone for gating.</violation>
</file>